ZodError.errors was removed in Zod 4; this repo is on zod 4.4.3.
packages/types/examples/zod-validation-example.ts
read .errors in seven places. Six printed undefined; the seventh —
invalidButtonResult.error.errors.length — threw, killing the example before its summary.

Confirmed empirically on 4.4.3 rather than assumed:

zod version: 4.4.3
.errors  -> undefined
.issues  -> ["invalid_value"]
.errors.length THREW -> TypeError: Cannot read properties of undefined (reading 'length')

And on the file itself, before the fix:

TypeError: Cannot read properties of undefined (reading 'length')
    at .../packages/types/examples/zod-validation-example.ts:182:79

After: it runs clean end-to-end and prints Expected validation errors: 2.

Same bug, same cause as the objectui validate fix in #2919 / #2936, used as the reference.

src/zod/README.md carried the same dead accessor plus a Zod 3 issue shape
(code: 'invalid_enum_value', "Invalid enum value. Expected …"). Both corrected
against what 4.4.3 actually emits: code: 'invalid_value' with a values array and
'Invalid option: expected one of …'.

Decision 1 — swap and gate, because the swap alone would rot again

Not just .errors -> .issues. The file is invisible to CI, so nothing stops the next drift.

One correction to the framing in the issue: removing "examples" from packages/types/tsconfig.json's exclude would have changed nothing. That project's include is already ["src/**/*"], so the exclude entry is belt-and-braces. Examples also cannot simply join that project — it is the package build (tsc -> dist) with rootDir: "./src", composite and declaration, so example files are both outside rootDir and would emit into dist.

So: a separate emit-free tsconfig.examples.json over examples/**/*.ts, chained from the package script:

"type-check": "tsc --noEmit && tsc -p tsconfig.examples.json"

The example also now imports ../src/zod/index.zod instead of ../dist/zod/index.zod.js — matching its three sibling example files (dashboard.ts, login-form.ts, rest-data-source.ts, all on ../src/index) — so the check needs no prior build.

Verified the gate has teeth rather than trusting the green (the standard set by #2936): restoring .errors makes tsc -p tsconfig.examples.json fail with seven

TS2339: Property 'errors' does not exist on type 'ZodError<...>'

Decision 2 — other examples/ dirs: one shares the exclusion, none share the risk

Grepped error.errors repo-wide over tracked files. Three hits beyond this file:

On the directories themselves:

• Root examples/* — not a gap. All four are real workspace packages; byo-backend-console, console-starter and schema-catalog each already carry "type-check": "tsc --noEmit", so turbo run type-check covers them. hello-world has no build and no tsconfig and is the declared NOT_COMPILED exemption in check-type-check-coverage.mjs, re-validated on every run.
• packages/plugin-charts/examples/chart-examples.ts — the only other package-internal examples dir, and it does share the exclusion (include: ["src"]). But it carries no imports at all — 54 lines of bare exported object literals — so there is no API surface to go stale. I deliberately did not add a tsconfig there: with nothing typed, the check would pass regardless of drift, and a gate that cannot fail is worse than an honest gap. Making it meaningful means typing those literals against the chart schemas, which is real work outside this fix.

So the systemic hole is narrower than "examples are excluded": it is package-internal examples/ dirs inside a package whose type-check is scoped to src. That set is exactly two, and only one had teeth to gain.

Verification

• pnpm --filter @object-ui/types type-check — passes (both projects)
• node scripts/check-type-check-coverage.mjs — 41/45, unchanged (no package count change)
• npx eslint packages/types — 0 errors (263 pre-existing no-explicit-any warnings in untouched src/)
• Example runs clean end-to-end under tsx

No runtime or published-type change — examples/ is not in the package's files.

🤖 Generated with Claude Code